home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000343_news@columbia.edu_Tue Sep 12 10:19:34 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA16925
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Tue, 12 Sep 1995 06:19:39 -0400
Received: by apakabar.cc.columbia.edu id AA04404
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Tue, 12 Sep 1995 06:19:37 -0400
Path: news.columbia.edu!merhaba.cc.columbia.edu!chaiklin
From: chaiklin@columbia.edu (Seth Chaiklin)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-KERMIT 3.14 hanging on idle TCP/IP connection?
Date: 12 Sep 1995 10:19:34 GMT
Organization: Columbia University
Lines: 72
Message-Id: <433mrn$49i@apakabar.cc.columbia.edu>
References: <42d2u9$edt@apakabar.cc.columbia.edu> <42dodl$go@apakabar.cc.columbia.edu> <2979@sun3.ipswitch.com>
Nntp-Posting-Host: merhaba.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <2979@sun3.ipswitch.com>, Dan Lanciani <ddl@harvard.edu> wrote:
[stuff deleted about how a MSK machine would lose control of the
terminal output after about 10 minutes and the ARP cache on a Linux
(1.2.8) machine would lose the hardware address of the MSK machine. ]
>You'd need a network trace to be sure, but this suggests that kermit
>isn't responding to ARPs in its current state.
I have traceroute and netstat (and maybe some others) on the Linux box.
It was mentioned that this could be helpful, but I do not know what I should
do or what I should look for.
>There are at least two additional experiments that might shed light on
>the situation.
>First, while in the bad state, try to ping it from another machine that
>has never been involved with the connection at all. This should tell
>you whether kermit is willing to respond to anybody's ARP at this point.
I did try this, and the MSK machine responded to the ping, so there was no
need to try the second test.
I also tried to ping from the Linux box, but there was no response.
However, if I handloaded the Hardware address of the ethernet
card on the MSK machine, then I could get a ping response.
However, this handloading technique does not always result in control being
returned to the MSK machine, as I once reported.
Meanwhile, some more information. After the MSK machine would not
respond (this again means, no output on the screen. It is still possible
to shell out to DOS, issue commands to the Linux box (as confirmed with a
'w' command from the console) etc., etc.), I tried to telnet to the same
Linux machine as well as other machines. I got the error message:
Unable to ARP resolve gateway
This was when I tried to ping from the Linux machine (with no response).
I tried another experiment. I logged in from the MSK machine, then immediately
deleted the entry from the Linux ARP cache. The output stopped, as other
times. It was still possible to telnet to other machines, but now it was
impossible to telnet to the Linux machine, no error message or anything, just
a return to the Kermit prompt.
Finally, I hand-entered the hw address for the MSK machine, and now I have
tried two or three times to let the MSK machine sit for for 30-60 minutes,
and I have not been able to reproduce the problem. It sounds like I
should just try to load the addresses for these cards, maybe even as a
cron job...but I would still like to try to understand what is going wrong.
I noticed in a recent message that there was an updated version of Kermit.
I use a version from 18 Jan 95. Could this also be a possible source of the
problem?
So I put a copy of 21 May 1995 onto the MSK machine. Tried to connect to
the Linux box and got: Unable to ARP resolve xxx.yyy.xxx.zzz
However, I was able to telnet to other machines.
Aaarrgh! I am really interested in solving this problem because we
would like to use 8-bit characters, and other telnet programs do not
behave as well as Kermit about this.
Also, when these "freeze-ups" do happen, it does not seem proper that
MS-Kermit should lockup on "exit" or "hangup" requiring a power-down
to restart the machine. I just wanted to re-emphasize that point.
Thanks for your patience with this jumbled and unclear information.
Cheers,
Seth Chaiklin